The Helix QAC software is designed to work with existing code projects, reading the existing code build configuration to gather the information that it needs: that is, source files, Include paths, environment settings, and other relevant details.
The Helix QAC software does this by executing a build of your code project. The software requires a single build command that can be run from anywhere on the system, and that will build the code project.
This is best explained through simple use cases. Examples are presented for both Linux and Windows. Much of the discussion is applicable to both, so, even if you intend to work solely on one system, it may be informative to read all the examples.
The examples in this guide assume you are using a static CCT i.e. a compiler definition we ship with each release. A newer, more automated method is now available for some compilers, called Auto CCTs. For more information on both these methods, see the chapter on Compiler Compatibility Templates (CCTs) in the Helix QAC user manual.
- GUI Use Case - Analyze a Simple Code Project built using an Executable Script on Linux
- CLI Use Case - Analyze a simple code project built using an executable script on a Linux PC
- Use Case - Analyze a Code Project Built using an Executable Script on Windows
- Use Case - Analyze a Microsoft VS Project without using the VS Plug-in
- Use Case - Synchronization of a Microsoft VS Project without Building the VS Project
- Use Case - Create a Helix QAC Project Manually using File Selection